<html>
<head><meta charset="utf-8"><title>end-user docs and futures · wg-async-foundations · Zulip Chat Archive</title></head>
<h2>Stream: <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/index.html">wg-async-foundations</a></h2>
<h3>Topic: <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html">end-user docs and futures</a></h3>

<hr>

<base href="https://rust-lang.zulipchat.com">

<head><link href="https://rust-lang.github.io/zulip_archive/style.css" rel="stylesheet"></head>

<a name="166743582"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166743582" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166743582">(May 28 2019 at 18:09)</a>:</h4>
<p>One thing I am wondering about, that relates to what <span class="user-mention" data-user-id="215333">@Florian Gilcher</span> was saying. I've talked to a few people who tried to put async-await to work, and they usually wind up getting stuck in/around the futures library -- e.g., discovering things like the <code>boxed()</code> combinator.</p>



<a name="166743669"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166743669" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166743669">(May 28 2019 at 18:10)</a>:</h4>
<p>Based on this, I have the feeling that (a) futures 1.0 stabilization is something we should definitely be paying a lot of attention to in the near future, and (b) there is likely a lot of docs we could write in this area.</p>



<a name="166743695"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166743695" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166743695">(May 28 2019 at 18:10)</a>:</h4>
<p>(Another question I'm wondering about is whether we can ask people to just tell us the kinds of things they got confused about and would have like to see documented)</p>



<a name="166743798"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166743798" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Nemo157 <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166743798">(May 28 2019 at 18:11)</a>:</h4>
<p>I have definitely noticed this as well on discord, a lot of questions can be answered with "here's the combinator from <code>futures</code> you need"</p>



<a name="166743887"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166743887" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Florian Gilcher <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166743887">(May 28 2019 at 18:12)</a>:</h4>
<p>BTW, I ported my standard example from my workshop over to runtime + futures and it works quite nicely. <a href="https://github.com/ferrous-systems/rust-three-days-course/blob/master/example/redisish-server/with-runtime/mailbox/src/main.rs" target="_blank" title="https://github.com/ferrous-systems/rust-three-days-course/blob/master/example/redisish-server/with-runtime/mailbox/src/main.rs">https://github.com/ferrous-systems/rust-three-days-course/blob/master/example/redisish-server/with-runtime/mailbox/src/main.rs</a></p>



<a name="166743897"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166743897" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Nemo157 <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166743897">(May 28 2019 at 18:12)</a>:</h4>
<p>also, basic documentation on how to work with pinned variables, like using <code>Box::pin</code> over <code>Box::new</code></p>



<a name="166743922"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166743922" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Florian Gilcher <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166743922">(May 28 2019 at 18:13)</a>:</h4>
<p>Found 2 confusing things, but nothing serious.</p>



<a name="166743940"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166743940" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Florian Gilcher <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166743940">(May 28 2019 at 18:13)</a>:</h4>
<p><span class="user-mention" data-user-id="210267">@Nemo157</span> what would be a case where users need a Pin?</p>



<a name="166743974"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166743974" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Nemo157 <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166743974">(May 28 2019 at 18:13)</a>:</h4>
<p>most commonly when working with generic <code>impl Future</code>/<code>impl Stream</code></p>



<a name="166744057"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166744057" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Nemo157 <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166744057">(May 28 2019 at 18:14)</a>:</h4>
<p>I guess <code>impl Future</code> is taken care of in async/await by <code>.await</code>, but having to pin a stream is not uncommon</p>



<a name="166744102"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166744102" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166744102">(May 28 2019 at 18:15)</a>:</h4>
<p>I am wondering whether we can show a lot of the examples we would need be using runtime's current support -- it certainly seems like we could show the various combinators and things that way</p>



<a name="166744117"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166744117" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Nemo157 <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166744117">(May 28 2019 at 18:15)</a>:</h4>
<p>probably the major thing is trying to return boxed futures, <code>Box&lt;dyn Future&gt;</code> is unusable, which is why there's the <code>BoxFuture</code> type alias</p>



<a name="166744126"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166744126" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166744126">(May 28 2019 at 18:15)</a>:</h4>
<p>for some more advanced things, like the specifics of dealing with HTTP etc, I guess that depends on whether one is using tokio, tide, etc -- for that we might redirect to the docs from each project</p>



<a name="166744248"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166744248" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166744248">(May 28 2019 at 18:17)</a>:</h4>
<blockquote>
<p>BTW, I ported my standard example from my workshop over to runtime + futures and it works quite nicely. </p>
</blockquote>
<p>I am partly going from "experience reports" from wycats + <span class="user-mention" data-user-id="132906">@Jonathan Turner</span> porting over their <a href="https://github.com/wycats/nushell" target="_blank" title="https://github.com/wycats/nushell">nushell project</a></p>



<a name="166744283"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166744283" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166744283">(May 28 2019 at 18:17)</a>:</h4>
<p>where it seemed like they hit a number of confusing things that they overcame but where docs would have been useful</p>



<a name="166744555"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166744555" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> David Barsky <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166744555">(May 28 2019 at 18:20)</a>:</h4>
<p>Some things I've ran into that I suspect others would also run into are:<br>
1. how to write a trait that returns an Future. I've ended up using <code>BoxFuture</code>.<br>
2. developing an intuitution as to when you need to use <code>Pin</code>, e.g., <code>pin_mut!</code>. I've sidestepped that issue for now in <a href="https://github.com/davidbarsky/proto-lambda" target="_blank" title="https://github.com/davidbarsky/proto-lambda">https://github.com/davidbarsky/proto-lambda</a> by using <code>BoxFuture</code>, but that's because I afford a heap allocation. Not everybody can.<br>
3. more generally with async/await—the top-level function _must_ async, hence runtime and friends.</p>



<a name="166744556"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166744556" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Nemo157 <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166744556">(May 28 2019 at 18:20)</a>:</h4>
<p><span class="user-mention" data-user-id="116009">@nikomatsakis</span> did they make public posts, or is that just from discussion?</p>



<a name="166744601"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166744601" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166744601">(May 28 2019 at 18:21)</a>:</h4>
<p>oh, just private discussion</p>



<a name="166744632"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166744632" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166744632">(May 28 2019 at 18:21)</a>:</h4>
<p>(I don't know any details, the only thing I remember had to do w/ boxed)</p>



<a name="166744793"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166744793" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Nemo157 <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166744793">(May 28 2019 at 18:23)</a>:</h4>
<p>Paragraph starting "Some more on pinning overall:" in <a href="https://internals.rust-lang.org/t/async-await-experience-reports/10200/14" target="_blank" title="https://internals.rust-lang.org/t/async-await-experience-reports/10200/14">https://internals.rust-lang.org/t/async-await-experience-reports/10200/14</a> is a pretty good commentary on current pinning documentation</p>



<a name="166744964"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166744964" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Taylor Cramer <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166744964">(May 28 2019 at 18:25)</a>:</h4>
<p>Yup, I'd love if we could have <code>rustc_on_unimplemented</code> for <code>Unpin</code> point to <code>pin_mut!</code> and <code>Box::pin</code>, but unfortunately the former is a 3p crate, so that wouldn't work out</p>



<a name="166745019"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166745019" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> David Barsky <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166745019">(May 28 2019 at 18:25)</a>:</h4>
<p><span class="user-mention" data-user-id="210267">@Nemo157</span> Thanks for the link! I think their experiences with pinning should be front-and-center in the futures documentation. I can see an argument for <code>pin_mut!</code> for being folded in the futures crate.</p>



<a name="166745038"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166745038" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Taylor Cramer <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166745038">(May 28 2019 at 18:25)</a>:</h4>
<p><span class="user-mention" data-user-id="198819">@David Barsky</span> fwiw it used to be</p>



<a name="166745095"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166745095" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Taylor Cramer <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166745095">(May 28 2019 at 18:26)</a>:</h4>
<p>before it got pulled out into a separate crate</p>



<a name="166745143"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166745143" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> David Barsky <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166745143">(May 28 2019 at 18:26)</a>:</h4>
<p><span class="user-mention" data-user-id="127859">@Taylor Cramer</span>  I'm not sure of the reasoning behind that, but absent any other evidence, bringing <code>pin_mut!</code> back into futures would be a win, IMO.</p>



<a name="166745167"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166745167" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Nemo157 <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166745167">(May 28 2019 at 18:27)</a>:</h4>
<p>it could at least be re-exported since it's almost always useful to users</p>



<a name="166745191"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166745191" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> David Barsky <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166745191">(May 28 2019 at 18:27)</a>:</h4>
<p>regarding pointing to <code>pin_mut!</code>—could a clippy lint provide that information?</p>



<a name="166745306"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166745306" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Taylor Cramer <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166745306">(May 28 2019 at 18:28)</a>:</h4>
<p>not sure how clippy would help since once you run clippy you've already got it compiling</p>



<a name="166745346"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166745346" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Taylor Cramer <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166745346">(May 28 2019 at 18:29)</a>:</h4>
<p>RE "not sure of the reasoning" it's because <code>pin_utils</code> is all general-purpose utils for Pin</p>



<a name="166745366"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166745366" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Taylor Cramer <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166745366">(May 28 2019 at 18:29)</a>:</h4>
<p>they don't interact directly with <code>std::future/task</code> at all</p>



<a name="166745387"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166745387" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> David Barsky <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166745387">(May 28 2019 at 18:29)</a>:</h4>
<p>ah, yes—true about the reasoning. forgot about non-futures use-cases for Pin.</p>



<a name="166745871"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166745871" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Florian Gilcher <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166745871">(May 28 2019 at 18:35)</a>:</h4>
<p><span class="user-mention" data-user-id="198819">@David Barsky</span> I think _most_ people can waste an allocation, it's totally fair for beginners documentation to go down that route.</p>



<a name="166746267"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/187312-wg-async-foundations/topic/end-user%20docs%20and%20futures/near/166746267" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> David Barsky <a href="https://rust-lang.github.io/zulip_archive/stream/187312-wg-async-foundations/topic/end-user.20docs.20and.20futures.html#166746267">(May 28 2019 at 18:39)</a>:</h4>
<p>That's true! Unrelated, but it's for that reason I've wanted the <code>~</code> operator to return as an alias for Box. The syntactic overhead of  <code>Box</code> dissuades people from heap allocating more than they should, IMO</p>



<hr><p>Last updated: Aug 07 2021 at 22:04 UTC</p>
</html>